Improve branch and path coverage presentation in HTML report#1141
Draft
sebastianbergmann wants to merge 8 commits into
Draft
Improve branch and path coverage presentation in HTML report#1141sebastianbergmann wants to merge 8 commits into
sebastianbergmann wants to merge 8 commits into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1141 +/- ##
============================================
- Coverage 98.04% 97.97% -0.08%
- Complexity 1622 1677 +55
============================================
Files 114 115 +1
Lines 5429 5632 +203
============================================
+ Hits 5323 5518 +195
- Misses 106 114 +8 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
sebastianbergmann
force-pushed
the
feature/branch-path-coverage-improvements
branch
from
7d46249 to
50f1729
Compare
Owner
Author
sebastianbergmann
force-pushed
the
feature/branch-path-coverage-improvements
branch
from
50f1729 to
911a937
Compare
sebastianbergmann
force-pushed
the
feature/branch-path-coverage-improvements
branch
2 times, most recently
from
4107924 to
59f5c88
Compare
sebastianbergmann
force-pushed
the
feature/branch-path-coverage-improvements
branch
from
59f5c88 to
6a2617f
Compare
sebastianbergmann
force-pushed
the
feature/branch-path-coverage-improvements
branch
2 times, most recently
from
a557754 to
a6ab506
Compare
…, and path coverage
sebastianbergmann
force-pushed
the
feature/branch-path-coverage-improvements
branch
from
a6ab506 to
d6ca908
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This intends to make the branch and path coverage views in the HTML code coverage report significantly easier to read and act on.
Source view gutter column
All three source views (line, branch, path) now include a narrow gutter column between the line number and the source code.
In the branch view, this column displays the direction indicators described above. In the line and path views, the column is present but hidden to keep the layout consistent across view tabs.
Inline branch direction indicators
The branch coverage source view now shows colored markers in the gutter at decision-point lines (lines where code can take multiple directions, such as
if/elseexpressions). Each marker represents one branch direction: green for covered, red for uncovered.Coverage badges on method headings
Each method heading in the branch and path structure sections now shows a coverage badge color-coded green, yellow, or red. This provides a quick at-a-glance summary of how well each method's branches or paths are covered, without needing to scan through the full table.
Path rendering no longer refuses to render
Previously, methods with more than 100 code paths showed only a message saying "too many paths to sensibly render." Now the full path table is always rendered. For methods with many paths, the table is wrapped in a collapsible section (collapsed by default) so the page remains navigable while still providing access to all the data.